Updating parameters in a mesh network

ABSTRACT

A method including communicating, by a first device, data with a second device based at least in part on communication information indicating a communication parameter associated with the second device, the data being communicated over a meshnet connection associated with a mesh network; receiving, by the first device while communicating the data in the mesh network, updated communication information indicating an updated communication parameter associated with the second device; and communicating, by the first device, the data with the second device over the meshnet connection based at least in part on the updated communication information. Various other aspects are contemplated.

CROSS REFERENCE

This application is a continuation of U.S. Non-Provisional patentapplication Ser. No. 17/559,939, filed on Dec. 22, 2021, and titled“Updating Parameters In A Mesh Network,” the entire contents of whichare incorporated herein by reference.

FIELD OF DISCLOSURE

Aspects of the present disclosure generally relate to providing secureprivate networks, and more particularly to enabling a hybrid meshnetwork.

BACKGROUND

Users may rely on mesh networks (also referred to as “meshnets”) tocommunicate (e.g., transmit and/or receive) data among a plurality ofendpoints (e.g., user devices) via one or more Internet nodes (e.g.,bridges, switches, infrastructure devices, etc.). In an example, a meshnetwork may include a plurality of endpoints communicatively coupled toeach other directly or via the one or more Internet nodes. A meshnetwork in which all endpoints are communicatively coupled to each othermay be referred to as a fully connected network. Data transmitted by afirst endpoint, from among the plurality of endpoints, may be routedover the Internet via the one or more Internet nodes to a secondendpoint from among the plurality of endpoints. Also, data transmittedby the first endpoint may be routed to two or more endpoints from amongthe plurality of endpoints.

In a mesh network, the plurality of endpoints may cooperate with eachother to enable communication of the data among the plurality ofendpoints. In an example, one or more of the endpoints may participatein communication of the data. In this way, the mesh network may avoidrelying on a given endpoint for communication of the data. Some meshnetworks may have the ability to dynamically self-organize andself-configure the plurality of endpoints. This ability may allow suchmesh networks to enable dynamic distribution of workloads, particularlyin the event that one or more endpoints should fail. Further,installation overhead may be reduced.

SUMMARY

In one aspect, the present disclosure contemplates a method includingdetermining, by a processor, first communication information indicatinga first communication parameter associated with a first device andsecond communication information indicating a second communicationparameter associated with a second device; transmitting, by theprocessor, the first communication information to the second device andthe second communication information to the first device to enable thefirst device and the second device to be included in a mesh network;determining, by the processor during communication between the firstdevice and the second device in the mesh network, updated firstcommunication information indicating an updated first communicationparameter associated with the first device and updated secondcommunication information indicating an updated second communicationparameter associated with the second device; and transmitting, by theprocessor, the updated first communication information to the seconddevice and the updated second communication information to the firstdevice.

In another aspect, the present disclosure contemplates a first deviceincluding a memory and a processor configured to: determine firstcommunication information indicating a first communication parameterassociated with a first device and second communication informationindicating a second communication parameter associated with a seconddevice; transmit the first communication information to the seconddevice and the second communication information to the first device toenable the first device and the second device to be included in a meshnetwork; determine, during communication between the first device andthe second device in the mesh network, updated first communicationinformation indicating an updated first communication parameterassociated with the first device and updated second communicationinformation indicating an updated second communication parameterassociated with the second device; and transmit the updated firstcommunication information to the second device and the updated secondcommunication information to the first device.

In another aspect, the present disclosure contemplates a non-transitorycomputer readable medium storing instructions, which when executed by aprocessor associated with a first device, cause the processor to:determine first communication information indicating a firstcommunication parameter associated with a first device and secondcommunication information indicating a second communication parameterassociated with a second device; transmit the first communicationinformation to the second device and the second communicationinformation to the first device to enable the first device and thesecond device to be included in a mesh network; determine, duringcommunication between the first device and the second device in the meshnetwork, updated first communication information indicating an updatedfirst communication parameter associated with the first device andupdated second communication information indicating an updated secondcommunication parameter associated with the second device; and transmitthe updated first communication information to the second device and theupdated second communication information to the first device.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory innature and are intended to provide an understanding of the presentdisclosure without limiting the scope thereof. In that regard,additional aspects, features, and advantages of the present disclosurewill be apparent to one skilled in the art from the following detaileddescription.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate aspects of systems, devices,methods, and/or mediums disclosed herein and together with thedescription, serve to explain the principles of the present disclosure.Throughout this description, like elements, in whatever aspectdescribed, refer to common elements wherever referred to and referencedby the same reference number. The characteristics, attributes,functions, interrelations ascribed to a particular element in onelocation apply to those elements when referred to by the same referencenumber in another location unless specifically stated otherwise.

The figures referenced below are drawn for ease of explanation of thebasic teachings of the present disclosure; the extensions of the figureswith respect to number, position, relationship, and dimensions of theparts to form the following aspects may be explained or may be withinthe skill of the art after the following description has been read andunderstood. Further, exact dimensions and dimensional proportions toconform to specific force, weight, strength, and similar requirementswill likewise be within the skill of the art after the followingdescription has been read and understood.

The following is a brief description of each figure used to describe thepresent disclosure, and thus, is being presented for illustrativepurposes only and should not be limitative of the scope of the presentdisclosure.

FIG. 1 is an illustration of an example system associated with updatingparameters in a mesh network, according to various aspects of thepresent disclosure.

FIG. 2 is an illustration of an example associated with updatingparameters in a mesh network, according to various aspects of thepresent disclosure.

FIG. 3 is an illustration of an example flow associated with updatingparameters in a mesh network, according to various aspects of thepresent disclosure.

FIG. 4 is an illustration of an example process associated with updatingparameters in a mesh network, according to various aspects of thepresent disclosure.

FIG. 5 is an illustration of an example process associated with updatingparameters in a mesh network, according to various aspects of thepresent disclosure.

FIG. 6 is an illustration of an example process associated with updatingparameters in a mesh network, according to various aspects of thepresent disclosure.

FIG. 7 is an illustration of an example process associated with updatingparameters in a mesh network, according to various aspects of thepresent disclosure.

FIG. 8 is an illustration of example devices associated with updatingparameters in a mesh network, according to various aspects of thepresent disclosure.

DETAILED DESCRIPTION

For the purposes of promoting an understanding of the principles of thepresent disclosure, reference will now be made to the aspectsillustrated in the drawings, and specific language may be used todescribe the same. It will nevertheless be understood that no limitationof the scope of the disclosure is intended. Any alterations and furthermodifications to the described devices, instruments, methods, and anyfurther application of the principles of the present disclosure arefully contemplated as would normally occur to one skilled in the art towhich the disclosure relates. In particular, it is fully contemplatedthat the features, components, and/or steps described with respect toone aspect may be combined with the features, components, and/or stepsdescribed with respect to other aspects of the present disclosure. Forthe sake of brevity, however, the numerous iterations of thesecombinations may not be described separately. For simplicity, in someinstances the same reference numbers are used throughout the drawings torefer to the same or like parts.

FIG. 1 is an illustration of an example 100 associated with updatingparameters in a mesh network, according to various aspects of thepresent disclosure. Example 100 shows an architectural depiction ofincluded components. In some aspects, the components may include one ormore user devices 102 capable of communicating with a mesh networkservice provider (MSP) control infrastructure 104 for purposes ofobtaining mesh network services. In some aspects, the one or more userdevices 102 may communicate with the MSP control infrastructure 104 overa network 118. The MSP control infrastructure 104 may be controlled by amesh network service provider and may include an application programminginterface (API) 106, a user database 108, processing unit 110, and ameshnet database 112. In some aspects, a user device 102 may utilize aprocessing unit 116 and/or a client application 114, which is providedby the MSP control infrastructure 104, to communicate with the API 106.The API 106 may be capable of communicating with the user database 108and with the processing unit 110. Additionally, the processing unit 110may be capable of communicating with the meshnet database 112, which maybe capable of storing data associated with providing mesh networkservices.

The user device 102 may be a physical computing device capable ofhosting the client application 114 and of connecting to the network 118.The user device 102 may be, for example, a laptop, a mobile phone, atablet computer, a desktop computer, a smart device, a router, or thelike. In some aspects, the user device 102 may include, for example,mesh network enabled Internet-of-Things (IoT) devices such as smart homeappliances, smart home security systems, autonomous vehicles, smarthealth monitors, smart factory equipment, wireless inventory trackers,biometric cyber security scanners, or the like. The network 118 may beany digital telecommunication network that permits several nodes toshare and access resources. In some aspects, the network 118 may includeone or more of, for example, a local-area network (LAN), a wide-areanetwork (WAN), a campus-area network (CAN), a metropolitan-area network(MAN), a home-area network (HAN), Internet, Intranet, Extranet, andInternetwork.

The MSP control infrastructure 104 may include a combination of hardwareand software components that enable provision of mesh network servicesto the user device 102. The MSP control infrastructure 104 may interfacewith (the client application on) the user device 102 via the API 106,which may include one or more endpoints to a defined request-responsemessage system. In some aspects, the API 106 may be configured toreceive, via the network 118, a connection request from the user device102 to establish a connection with the MSP control infrastructure 104for purposes of obtaining the mesh network services. The connectionrequest may include an authentication request to authenticate the userdevice 102. The API 106 may receive the authentication request and arequest for the mesh network services in a single connection request. Insome aspects, the API 106 may receive the authentication request and therequest for the mesh network services in separate connection requests.

The API 106 may further be configured to handle the connection requestby mediating the authentication request. For instance, the API 106 mayreceive from the user device 102 credentials including, for example, aunique combination of a user ID and password for purposes ofauthenticating the user device 102. In another example, the credentialsmay include a unique validation code known to an authentic user. The API106 may provide the received credentials to the user database 108 forverification.

The user database 108 may include a structured repository of validcredentials belonging to authentic users. In one example, the structuredrepository may include one or more tables containing valid uniquecombinations of user IDs and passwords belonging to authentic users. Inanother example, the structured repository may include one or moretables containing valid unique validation codes associated withauthentic users. The mesh network service provider may add or deletesuch valid unique combinations of user IDs and passwords from thestructured repository at any time. Based at least in part on receivingthe credentials from the API 106, the user database 108 and a processor(e.g., the processing unit 110 or another local or remote processor) mayverify the received credentials by matching the received credentialswith the valid credentials stored in the structured repository. In someaspects, the user database 108 and the processor may authenticate theuser device 102 when the received credentials match at least one of thevalid credentials. In this case, the mesh network service provider mayprovide mesh network services to the user device 102. When the receivedcredentials fail to match at least one of the valid credentials, theuser database 108 and the processor may fail to authenticate the userdevice 102. In this case, the mesh network service provider may declineto provide mesh network services to the user device 102.

When the user device 102 is authenticated, the user device 102 mayinitiate a connection and may transmit to the API 106 a request for themesh network services. The processing unit 110 included in the MSPcontrol infrastructure 104 may be configured to determine a mesh networkassociated with the user device 102 and/or to identify one or more userdevices to be included within the determined mesh network. Theprocessing unit 110 may utilize the API 106 to transmit informationassociated with the mesh network and/or the identified one or more userdevices to the user device 102. The user device 102 may transmit aninitiation request to establish secure connections (e.g., encryptedtunnels) with the one or more user devices. In some aspects, the one ormore user devices with which the user device 102 establishes the secureconnections may also host respective client applications forcommunicating with the MSP control infrastructure 104 and/or with theuser device 102. In some aspects, the processing unit 110 may be alogical unit including a logical component configured to perform complexoperations associated with computing, for example, numerical weightsrelated to various factors associated with providing the meshnetservices.

One or more components (e.g., API 106, user database 108, processingunit 110, and/or meshnet database 112, processing unit 116) included inthe MSP control infrastructure 104 and/or included in the user device102 may further be associated with a controller/processor, a memory, acommunication interface, or a combination thereof (e.g., FIG. 8 ). Forinstance, the one or more components of the set of components mayinclude or may be included in a controller/processor, a memory, or acombination thereof. In some aspects, the one or more of the componentsincluded in the MSP control infrastructure 104 and/or the user device102 may be separate and distinct from each other. Alternatively, in someaspects, one or more of the components included in the MSP controlinfrastructure 104 and/or the user device 102 may be combined with oneor more of other components included in the MSP control infrastructure104. In some aspects, the one or more of the components included in theMSP control infrastructure 104 and/or the user device 102 may be localwith respect to each other. Alternatively, in some aspects, one or moreof the components included in the MSP control infrastructure 104 and/orthe user device 102 may be located remotely with respect to one or moreof other components included in the MSP control infrastructure 104and/or the user device 102. Additionally, or alternatively, one or morecomponents of the components included in the MSP control infrastructure104 and/or the user device 102 may be implemented at least in part assoftware stored in a memory. For example, a component (or a portion of acomponent) may be implemented as instructions or code stored in anon-transitory computer-readable medium and executable by a controlleror a processor to perform the functions or operations of the component.Additionally, or alternatively, a set of (one or more) components shownin FIG. 1 may be configured to perform one or more functions describedas being performed by another set of components shown in FIG. 1 .

As indicated above, FIG. 1 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 1 .

Endpoints (e.g., user devices) may rely on a mesh network to communicate(e.g., transmit and/or receive) data among the endpoints. In example 200shown in FIG. 2 , the endpoints may include a first user device, asecond user device, a third user device, and/or a fourth user device.The data may be communicated using wired communications and/or wirelesscommunications over a network such as, for example, the Internet. Thecommunicated data may include any information including digitalinformation such as, for example, documents including data, voice data,image data, signal data, and/or video data. Further, the internal meshnetwork may be a secure mesh network that may enable the endpoints tocommunicate the data in encrypted form via meshnet connections (shown asdouble-ended arrows in FIG. 2 ).

The endpoints may utilize a user datagram protocol (UDP) to communicatethe data over the meshnet connections. To utilize the UDP, each of theendpoints may be associated with a respective UDP Internet protocol (IP)address and a respective UDP port. For instance, the first user devicemay be associated with a first UDP IP address and a first UDP port forcommunicating the data, the second user device may be associated with asecond UDP IP address and a second UDP port for communicating the data,the third user device may be associated with a third UDP IP address anda third UDP port for communicating the data, and the fourth user devicemay be associated with a fourth UDP IP address and a fourth UDP port forcommunicating the data. During setup of the mesh network, each of theendpoints may receive communication information including, for example,the UDP IP address and the UDP port associated with each of the other ofthe endpoints to be utilized for communication.

The endpoints may communicate with each other based at least in part onthe communication information. In an example, with respect tocommunication between the first user device and the second user device,the first user device may utilize the first UDP port to transmit data inan IP packet to the second UDP port, the IP packet indicating the firstUDP IP address as a source address, the first UDP port as a source port,the second UDP IP address as a destination address, and the second UDPport as a destination port. The second user device may utilize thesecond UDP port to receive the IP packet. Similarly, with respect tocommunication between the third user device and the fourth user device,the fourth user device may utilize the fourth UDP port to transmit datain an IP packet to the third UDP port, the IP packet indicating thefourth UDP IP address as the source address, the fourth UDP port as thesource port, the third UDP IP address as the destination address, andthe third UDP port as the destination port. The third user device mayutilize the third UDP port to receive the IP packet.

During communication among the endpoints, the mesh network may fail. Inan example, due to independent network address translation (NAT)procedures, a UDP port associated with one or more of the endpoints maychange. For instance, a NAT device (e.g., router, etc.) associated witha given endpoint may reallocate a given UDP port associated with thegiven endpoint for a task other than communication in the mesh network.In some cases, such reallocation may be due to lack of communication inthe mesh network by the given endpoint for a threshold amount of time,due to a need for the given UDP port to support the task other thancommunication in the mesh network, network administration actions,NAT/router device reboot, and/or ISP actions. Because other endpoints inthe mesh network (and the given endpoint) are unaware of thereallocation of the given UDP port, communications from the otherendpoints transmitted to the given UDP port as the destination port mayfail. In this case, the other endpoints may retransmit thecommunications to the given endpoint to ensure receipt thereof by thegiven endpoint. Such transmission and retransmission of communicationsmay inefficiently consume user device resources (e.g., processingresources, memory resources, power consumption resources, battery life,or the like) and the network resources (computational resources, networkbandwidth, management resources, processing resources, memory resources,or the like) that can otherwise be used to perform suitable tasksassociated with the mesh network.

In another example, a given endpoint associated with a given UDP IPaddress may utilize a first technology (e.g., Wi-Fi technology) toaccess the Internet. The other endpoints in the mesh network may utilizethe given UDP IP address to communicate data with the given endpoint.While communicating the data in the mesh network, the given endpoint maychange its location, which may result in the given endpoint utilizing adifferent technology (e.g., mobile technology (e.g., LTE, CDMA, GSM,etc.)) to access the Internet. As a result, the given UDP IP address maychange to a new UDP IP address. Because the other endpoints in the meshnetwork may be unaware of the change in the second UDP IP address,communications from the other endpoints (utilizing the second UDP IPaddress as the destination address and not the new UDP IP address) mayfail to reach the given endpoint. The other endpoints may retransmitcommunications to the given endpoint to ensure receipt thereof by thegiven endpoint. Such transmission and retransmission of communicationsmay inefficiently consume user device resources (e.g., processingresources, memory resources, power consumption resources, battery life,or the like) and the network resources (computational resources, networkbandwidth, management resources, processing resources, memory resources,or the like) that can otherwise be used to perform suitable tasksassociated with the mesh network.

Various aspects of systems and techniques discussed in the presentdisclosure enable updating parameters in a mesh network. In someaspects, an MSP control infrastructure may provide the mesh network toenable the endpoints to securely communicate data. Further, the MSPcontrol infrastructure may provide the endpoints with respective clientapplications to communicate with the MSP control infrastructure, tocommunicate with each other for setting up respective meshnetconnections to be utilized for communicating the data in the meshnetwork, and to communicate with each other over the respective meshnetconnections in the mesh network. The MSP control infrastructure and therespective client applications may enable updating of communicationparameters (e.g., UDP IP addresses, UDP ports, etc.) associated with theendpoints. In some aspects, the MSP control infrastructure and therespective client applications periodically communicate informationregarding the parameters, thereby enabling updating of the parameters.In this way, the endpoints may communicate the data utilizing updatedparameters, thereby mitigating instances of inefficient transmissionsand retransmissions of communications among the endpoints. As a result,the MSP control infrastructure and the respective client applicationsmay enable efficient utilization of user device resources (e.g.,processing resources, memory resources, power consumption resources,battery life, or the like) and network resources (computationalresources, network bandwidth, management resources, processingresources, memory resources, or the like) for performing suitable tasksassociated with the secure mesh network.

In some aspects, a processor (e.g., processing unit 110, processor 820)associated with the MSP control infrastructure may determine firstcommunication information indicating a first communication parameterassociated with a first device and second communication informationindicating a second communication parameter associated with a seconddevice; transmit the first communication information to the seconddevice and the second communication information to the first device toenable the first device and the second device to be included in a meshnetwork; determine, during communication between the first device andthe second device in the mesh network, updated first communicationinformation indicating an updated first communication parameterassociated with the first device and updated second communicationinformation indicating an updated second communication parameterassociated with the second device; and transmit the updated firstcommunication information to the second device and the updated secondcommunication information to the first device.

As indicated above, FIG. 2 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 2 .

FIG. 3 is an illustration of an example flow 300 associated withupdating parameters in a mesh network, according to various aspects ofthe present disclosure. The example flow 300 may include a first userdevice (e.g., first endpoint), MSP control infrastructure 104, and asecond user device (e.g., second endpoint) in communication with eachother. The first user device and the second user device may be similarto a user device 102 discussed above with respect to FIG. 1 . In someaspects, the first user device and the second user device may beassociated with a single account registered with the MSP controlinfrastructure 104. In some aspects, the first user device and thesecond user device may be associated with different accounts registeredwith the MSP control infrastructure 104. In some aspects, the first userdevice and the second user device may be located locally (e.g., in thesame room, in the same building, etc.). In some aspects, the first userdevice and the second user device may be located remotely (e.g., indifferent buildings, in different cities, in different states, indifferent countries, etc.) with respect to each other. The first userdevice may install a first client application (e.g., client application114) and the second user device may install a second client application(e.g., client application 114), the first client application and thesecond client application being associated with (e.g., provided by) theMSP control infrastructure 104. The first user device and the seconduser device may use the respective client applications to communicatewith an application programming interface (API) and/or a processor(e.g., processing unit 110, processor 820) associated with the MSPcontrol infrastructure 104. In some aspects, the first user device, theMSP control infrastructure 104, and the second user device maycommunicate with each other over a network (e.g., network 118). In someaspects, as discussed elsewhere herein, the MSP control infrastructure104 may enable the first user device and/or the second user device toobtain the mesh network services. Although only two user devices (e.g.,endpoints) are discussed with respect to FIG. 3 , the present disclosurecontemplates the mesh network to include any number of user devices thatperform the processes discussed herein in a similar and/or analogousmanner.

In some aspects, the client applications may enable the user devices toreceive information to be processed by the client applications and/or bythe MSP control infrastructure 104. Each of the client applications mayinclude respective graphical user interfaces to receive the informationvia local input interfaces (e.g., touch screen, keyboard, mouse,pointer, etc.) associated with the user devices. The information may bereceived via text input or via a selection from among a plurality ofoptions (e.g., pull down menu, etc.). In some aspects, the first clientapplication and/or the second client application may activate and/orenable, at a time associated with the registration (e.g., after theregistration), the graphical interface for receiving the information.For instance, the first client application (or the second clientapplication) may cause a screen (e.g., local screen) associated with thefirst user device (or the second user device) to display, for example, apop-up message to request entry of the information. Further, the clientapplications may enable transmission of at least a portion of theinformation to the MSP control infrastructure 104. In some aspects, thefirst client application may utilize a first processing unit (e.g.,processing unit 116, processor 820) included in the first user device toperform processes/operations associated with obtaining the mesh networkservices and the second application may utilize a second processing unit(e.g., processing unit 116, processor 820) included in the second userdevice to perform processes/operations associated with obtaining themesh network services.

As shown by reference numeral 305, the first user device may register anaccount with the MSP control infrastructure 104. In some aspects, duringthe registration, the first user device may provide registrationinformation such as, for example, identity of an owner of the first userdevice, a phone number associated with the first user device, an emailaddress associated with the first user device, or the like. In someaspects, the first user device may set up an access system includinglogin information (e.g., access information) such as, for example,username, password, or the like to subsequently gain access to theregistered account. In some aspects, the first user device may share thelogin information with other user devices (e.g., second user device)associated with the first user device to enable the other user devicesto utilize the login information to gain access to the MSP controlinfrastructure 104 via the registered account. In some aspects, a givenuser device may be associated with the first user device because thegiven user device may be available to a user/owner of the first userdevice. In some aspects, when the second user device is not associatedwith the registered account associated with the first user device, thesecond user device may register a different account with the MSP controlinfrastructure 104.

In some aspects, the first user device and the second user device mayutilize the login information to access the registered account/accountsto communicate with the MSP control infrastructure 104. As shown byreference numeral 310, based at least in part on the first user deviceand the second user device accessing the registered account/accounts tocommunicate with the MSP control infrastructure 104, the MSP controlinfrastructure 104 may transmit, and the first client application andthe second client application may receive, MSP access information. Insome aspects, the MSP access information may include UDP accessinformation. The UDP access information may include informationregarding an infrastructure UDP IP address and an infrastructure UDPport associated with the MSP control infrastructure 104. The MSP controlinfrastructure 104 may utilize the infrastructure UDP IP address and theinfrastructure UDP port to communicate utilizing the UDP. In someaspects, the first user device and the second user device may utilizethe infrastructure UDP IP address and the infrastructure UDP port tocommunicate with the MSP control infrastructure 104 regarding the meshnetwork. Further, the first client application and the second clientapplication may obtain. from, for example, a domain name services (DNS)server, transmission control protocol (TCP) access informationassociated with the MSP control infrastructure 104. Such TCP accessinformation may include information regarding an infrastructure TCP IPaddress and an infrastructure TCP port associated with the MSP controlinfrastructure 104. The MSP control infrastructure 104 may utilize theinfrastructure TCP IP address and the infrastructure TCP port tocommunicate utilizing the TCP.

As shown by reference numeral 315, the first client application and thesecond client application may determine information based at least inpart on the registration of the account/accounts with the MSP ControlInfrastructure 104. In an example, the first client application maydetermine a first asymmetric assigned key pair associated with the firstuser device. The first assigned key pair may be unique to the first userdevice and may include a first assigned public key and a first assignedprivate key. In this way, the first assigned public key and the firstassigned private key may be device-specific and maybe associated withthe registered account. In some aspects, the first assigned public keyand the first assigned private key may be associated with each othervia, for example, a mathematical function. As a result, data encryptedusing the first assigned public key may be decrypted by utilizing thefirst assigned private key.

Similarly, the second client application may determine a secondasymmetric assigned key pair associated with the second user device. Thesecond assigned key pair may be unique to the second user device and mayinclude a second assigned public key and a second assigned private key.In this way, the second assigned public key and the second assignedprivate key may be device-specific and maybe associated with theregistered account. In some aspects, the second assigned public key andthe second assigned private key may be associated with each other via,for example, a mathematical function. As a result, data encrypted usingthe second assigned public key may be decrypted by utilizing the secondassigned private key.

As shown by reference numeral 320, the client applications may transmit,and the MSP control infrastructure 104 may receive, at least a portionof the information determined by the client applications. For instance,the first client application may transmit, for example, the firstassigned public key to the MSP control infrastructure 104 and the secondclient application may transmit, for example, the second assigned publickey to the MSP control infrastructure 104. The MSP controlinfrastructure 104 may store and correlate the received information inassociation with the registered account and/or with the respective userdevices. In an example, the MSP control infrastructure 104 may store andcorrelate the first assigned public key in association with theregistered account and the first user device, and may store andcorrelate the second assigned public key in association with theregistered account and the second user device. In some aspects, thefirst client application and the second client application may utilizethe infrastructure TCP IP address and the infrastructure TCP port totransmit the first assigned public key and the second assigned publickey to the MSP control infrastructure 104 via the TCP.

Further, as shown by reference numeral 325, the MSP controlinfrastructure 104 may determine that the first user device and thesecond user device are to be included in the same mesh network. In someaspects, when the first user device and the second user device areassociated with the same registered account, the MSP controlinfrastructure 104 may make such a determination regarding the securemesh network based at least in part on determining that the first userdevice and the second user device are communicating with the MSP controlinfrastructure 104 by utilizing the login information associated withthe same registered account. In some aspects, when the first user deviceand the second user device are associated with different registeredaccounts, the MSP control infrastructure 104 may make such adetermination regarding the secure mesh network based at least in parton the first user device (or the second user device) providinginformation indicating that the first user device and the second userdevice are to be included in the secure mesh network. Such informationmay include, for example, identification information (e.g., type ofdevice, etc.) associated with the second user device (or the first userdevice), the second IP address (or the first IP address), or the like.

Based at least in part on determining that the first user device and thesecond user device are to be included in the same mesh network, as shownby reference numeral 330, the MSP control infrastructure 104 maydetermine meshnet IP addresses for the first user device and for thesecond user device. In an example, the MSP control infrastructure 104may determine a first meshnet IP address associated with the first userdevice and a second meshnet IP address associated with the second userdevice. The first client application and/or another applicationinstalled on the first user device and/or the operating systemassociated with the first user device may utilize the first meshnet IPaddress and/or the first local meshnet port to communicate data with theendpoints over meshnet connections in the mesh network and the seconduser device may utilize the second meshnet IP address and/or the secondlocal meshnet port to communicate data with the endpoints over themeshnet connections in the mesh network. In an example, with respect tocommunication between the first user device and the second user device,the first user device may determine a first meshnet IP packet indicatingthe first meshnet IP address as a source address, the first localmeshnet port as a source port, the second meshnet IP address as adestination address, and the second local meshnet port as a destinationport. The first user device may encrypt and encapsulate the firstmeshnet IP packet within a payload of a transmitted UDP IP packet. Thesecond user device may receive the UDP IP packet, may decrypt the firstmeshnet IP packet, and may route the first meshnet IP packet to thesecond local meshnet port. Similarly, the second user device maydetermine a second meshnet IP packet indicating the second meshnet IPaddress as a source address, the second local meshnet port as a sourceport, the first meshnet IP address as a destination address, and thefirst local meshnet port as a destination port. The second user devicemay encrypt and encapsulate the second meshnet IP packet within apayload of a transmitted UDP IP packet. The first user device mayreceive the UDP IP packet, may decrypt the first meshnet IP packet, andmay route the second meshnet IP packet to the first local meshnet port.The MSP control infrastructure 104 may determine the first meshnet IPaddress and the second meshnet IP address from, for example, a pool ofreserved IP addresses included in a subnet associated with an internalnetwork of the ISP.

In some aspects, example processes associated with blocks 305 through330 may take place asynchronously. In some aspects, example processesassociated with blocks 335 and 355 may take place substantiallysynchronously.

As shown by reference numeral 335, the first user device and the seconduser device may transmit, and the MSP control infrastructure 104 mayreceive, respective binding requests. In an example, the first userdevice may transmit a first binding request to the MSP controlinfrastructure 104 to request the MSP control infrastructure 104 todetermine a first UDP IP address (e.g., communication address) and afirst UDP port (e.g., communication port) associated with the firstdevice. In some aspects, the first user device may transmit the firstbinding request to the MSP control infrastructure 104 using the UDP byutilizing the UDP access information received from the MSP controlinfrastructure 104 (e.g., block 310). As discussed below in furtherdetail, the first UDP IP address and the first UDP port are to beutilized by the second user device to communicate with the first userdevice in the mesh network. Similarly, the second user device maytransmit a second binding request to the MSP control infrastructure 104to request the MSP control infrastructure 104 to determine a second UDPIP address (e.g., communication address) and a second UDP port (e.g.,communication port) associated with the second device. In some aspects,the second user device may transmit the second binding request to theMSP control infrastructure 104 using the UDP by utilizing the UDP accessinformation received from the MSP control infrastructure 104 (e.g.,block 310). As discussed below in further detail, the second UDP IPaddress and the second UDP port are to be utilized by the first userdevice to communicate with the second user device in the mesh network.

In some aspects, the first UDP IP address and the first UDP port may bedetermined by a first NAT device responsible for managing operation ofthe first user device in a first local network. In an example, the firstNAT device may translate a first local UDP IP address and a first localUDP port associated with the first user device to the first UDP IPaddress and the first UDP port that the first user device utilizes tocommunicate (e.g., transmit and/or receive) over the Internet using theUDP. Similarly, the second UDP IP address and the second UDP port may bedetermined by a second NAT device responsible for managing operation ofthe second user device in a second local network. In an example, thesecond NAT device may translate a second local UDP IP address and asecond local UDP port associated with the second user device to thesecond UDP IP address and the second UDP port that the second userdevice utilized to communicate (e.g., transmit and/or receive) over theInternet using the UDP.

Based at least in part on receiving the respective binding requests, asshown by reference numeral 340, the MSP control infrastructure 104 maydetermine UDP IP addresses and UDP ports for the first user device andthe second user device. In an example, based at least in part onreceiving the first binding request, the MSP control infrastructure 104may determine the first UDP IP address and the first UDP port associatedwith the first user device. In some aspects, the MSP controlinfrastructure 104 may determine the first UDP IP address and the firstUDP port based at least in part on analyzing the UDP communication(e.g., UDP IP packet) including the first binding request received fromthe first user device. The UDP communication may include, for example, aheader that indicates the first UDP IP address as a source UDP IPaddress and the first UDP port as a source UDP port associated with thefirst user device. Further, the MSP control infrastructure 104 may storeand correlate the first UDP IP address and the first UDP port inassociation with the first user device in, for example, the meshnetdatabase 112. Similarly, based at least in part on receiving the secondbinding request, the MSP control infrastructure 104 may determine thesecond UDP IP address and the second UDP port associated with the seconduser device. In some aspects, the MSP control infrastructure 104 maydetermine the second UDP IP address and the second UDP port based atleast in part on analyzing the UDP communication (e.g., UDP IP packet)including the second binding request received from the second userdevice. The UDP communication may include, for example, a header thatindicates the second UDP IP address as a source UDP IP address and thesecond UDP port as a source UDP port associated with the second userdevice. Further, the MSP control infrastructure 104 may store andcorrelate the second UDP IP address and the second UDP port inassociation with the second user device in, for example, the meshnetdatabase 112.

Based at least in part on determining the UDP IP addresses and the UDPports, as shown by reference numeral 345, the MSP control infrastructure104 may transmit, and the first client application and the second clientapplication may receive, communication information. In an example, theMSP control infrastructure 104 may transmit, and the first clientapplication may receive, first communication information including thefirst meshnet IP address associated with the first user device, thesecond meshnet IP address associated with the second user device, thesecond UDP IP address and the second UDP port associated with the seconduser device, and the second public key associated with the second userdevice. Similarly, the MSP control infrastructure 104 may transmit, andthe second client application may receive, second communicationinformation including the first UDP IP address and the first UDP portassociated with the first user device, the first public key associatedwith the first user device, the first meshnet IP address associated withthe first user device, and the second meshnet IP address associated withthe second user device. As discussed below in further detail, the abovetransmission of communication information may enable the first userdevice and the second user device to communicate securely and privatelyin the mesh network.

As shown by reference numeral 350, the first user device and the seconduser device may communicate with each other to set up a meshnetconnection (e.g., an encrypted tunnel) for communicating encrypted datain the hybrid mesh network. To set up the meshnet connection, the firstclient application may utilize the second assigned public key and/or thesecond public IP address to securely (e.g., in encrypted form)communicate with the second user device, and the second clientapplication may utilize the first assigned public key and/or the firstpublic IP address to securely communicate with the first user device. Insome aspects, the first user device and the second user device maycommunicate to securely/privately negotiate parameters (e.g., asymmetric encryption/decryption key) associated with the meshnetconnection. In some aspects, the parameters may be randomly generated toprovide optimized security to the communications. In an example, thefirst user device and the second user device may privately negotiate arandomly generated symmetric key that is to be utilized by the firstuser device and the second user device for encrypting and decryptingdata communicated via the meshnet connection. The randomly generatedsymmetric key may be determined based at least in part on anycombination of the first public key, the second public key, and/orrandomly generated numbers. Additionally, the first user device and thesecond user device may utilize a secure protocol (e.g., Wireguard, IPsec, etc.) to communicate the data via the meshnet connection. Based atleast in part on setting up the meshnet connection, the first userdevice and the second user device may start communicating encrypted datavia the meshnet connection based at least in part on utilizing thenegotiated parameters and the secure protocol.

Further, based at least in part on setting up the meshnet connection, asshown by reference numeral 355, the first user device, the second userdevice, and the MSP control infrastructure 104 may enable updating ofthe UDP IP addresses and/or the UDP ports associated with the first userdevice and with the second user device. In some aspects, whilecommunicating data with the second user device via the meshnetconnection in the mesh network, the first client application maytransmit, and the MSP control infrastructure 104 may receive, a firstcurrent binding request to request the MSP control infrastructure 104 todetermine a current first UDP IP address (e.g., updated communicationaddress) and a current first UDP port (e.g., updated communication port)associated with the first device. In a similar and/or analogous manneras the first binding request discussed above with respect to block 335,the first client application may transmit the first current bindingrequest using the UDP by utilizing the UDP access information receivedfrom the MSP control infrastructure 104 (e.g., block 310).

Based at least in part on receiving the first current binding request,the MSP control infrastructure 104 may determine the current first UDPIP address and the current first UDP port associated with the first userdevice. In some aspects, the MSP control infrastructure 104 maydetermine the current first UDP IP address and the current first UDPport based at least in part on analyzing the UDP communication (e.g.,UDP IP packet) including the first current binding request received fromthe first user device. The UDP communication may include, for example, aheader that indicates the current first UDP IP address as a source UDPIP address and the current first UDP port as a source UDP portassociated with the first user device. Further, the MSP controlinfrastructure 104 may update the stored correlation of the first UDP IPaddress and the first UDP port in association with the first user devicein, for example, the meshnet database 112. In an example, the MSPcontrol infrastructure may replace the stored first UDP IP address andthe first UDP port with the current first UDP IP address and the currentfirst UDP port (e.g., updating the first correlation by replacing thefirst communication information with first updated communicationinformation). Further, based at least in part on determining the currentfirst UDP IP address and the current first UDP port, the MSP controlinfrastructure 104 may transmit, and the first client application and/orthe second client application may receive, first communicationinformation and/or second communication information, respectively,including the current first UDP IP address and the current first UDPport associated with the first user device. In some aspects, the MSPcontrol infrastructure 104 may update the stored correlation and/ortransmit the communication information when the MSP controlinfrastructure determines a change in the current first UDP IP addressand/or the current first UDP port associated with the first user device.

Similarly, while communicating data with the first user device via themeshnet connection in the mesh network, the second client applicationmay transmit, and the MSP control infrastructure 104 may receive, asecond current binding request to request the MSP control infrastructure104 to determine a current second UDP IP address (e.g., updatedcommunication address) and a current second UDP port (e.g., updatedcommunication port) associated with the second device. In a similarand/or analogous manner as the second binding request discussed abovewith respect to block 335, the second client application may transmitthe second current binding request using the UDP by utilizing the UDPaccess information received from the MSP control infrastructure 104(e.g., block 310).

Based at least in part on receiving the second current binding request,the MSP control infrastructure 104 may determine the current second UDPIP address and the current second UDP port associated with the seconduser device. In some aspects, the MSP control infrastructure 104 maydetermine the current second UDP IP address and the current second UDPport based at least in part on analyzing the UDP communication (e.g.,UDP IP packet) including the second current binding request receivedfrom the second user device. The UDP communication may include, forexample, a header that indicates the current second UDP IP address as asource UDP IP address and the current second UDP port as a source UDPport associated with the second user device. Further, the MSP controlinfrastructure 104 may update the stored correlation of the second UDPIP address and the second UDP port in association with the second userdevice in, for example, the meshnet database 112. In an example, the MSPcontrol infrastructure may replace the stored second UDP IP address andthe second UDP port with the current second UDP IP address and thecurrent second UDP port (e.g., updating the second correlation byreplacing the second communication information with the second updatedcommunication information). Further, based at least in part ondetermining the current second UDP IP address and the current second UDPport, the MSP control infrastructure 104 may transmit, and the firstclient application and/or the second client application may receive,first communication information and/or second communication information,respectively, including the current second UDP IP address and thecurrent second UDP port associated with the second user device. In someaspects, the MSP control infrastructure 104 may update the storedcorrelation and/or transmit the communication information when the MSPcontrol infrastructure determines a change in the current second UDP IPaddress and/or the current second UDP port associated with the firstuser device.

Based at least in part on (i) the first client application receiving thecurrent second UDP IP address and the current second UDP port and/or(ii) the second client application receiving the current first UDP IPaddress and the current first UDP port, the first client application andthe second client application may continue to securely communicate witheach other via the meshnet connection in the mesh network withoutinterruption.

In some aspects, the first client application may periodically transmitthe first current binding request and/or the second client applicationmay periodically transmit the second current binding request to the MSPcontrol infrastructure 104. Instances associated with periodicallytransmitting the first current binding request and/or the second currentbinding request may be, for example, every 15 seconds, every 25 seconds,every 35 seconds, every 45 seconds, every 60 seconds, every 120 seconds,etc.

Further, in some aspects, the first client application may refrain fromtransmitting, at a given instance, the first current binding requestbased at least in part on determining that a condition associated withtransmitting the first current binding request is satisfied. In anexample, the condition may be satisfied when the first clientapplication determines that the first client application is activelycommunicating data with the second client application (or anotherrespective client application associated with another user device in themesh network) during the given instance (e.g., at a time associated withoccurrence of the given instance). In another example, the condition maybe satisfied when the first client application determines that the firstclient application and/or another application installed on the firstuser device (e.g., web browser, etc.) does not anticipate communicatingdata with the second client application (or another respective clientapplication associated with another user device in the mesh network) fora given interval of time, and that the given instance is to occur withinthe given interval of time.

Similarly, the second client application may refrain from transmitting,at a given instance, the second current binding request based at leastin part on determining that a condition associated with transmitting thesecond current binding request is satisfied. In an example, thecondition may be satisfied when the second client application determinesthat the second client application is actively communicating data withthe first client application (or another respective client applicationassociated with another user device in the mesh network) during thegiven instance (e.g., at a time associated with occurrence of the giveninstance). In another example, the condition may be satisfied when thesecond client application determines that the second client applicationand/or another application installed on the second user device (e.g.,web browser, etc.) does not anticipate communicating data with the firstclient application (or another respective client application associatedwith another user device in the mesh network) for a given interval oftime, and that the given instance is to occur within the given intervalof time.

As discussed previously, the MSP control infrastructure 104 may storeand correlate the UDP IP addresses and the UDP ports associated with thefirst user device and the second user device (and other devices includedin the mesh network) in the meshnet database 112. In some aspects, themeshnet database 112 may be a cache-enabled time-based in-memory storagedevice to enable speedy retrieval of the stored and correlated data. Themeshnet database 112 may rely primarily on memory for data storage, andmay avoid relying on storing data on disk solutions and/or on solidstate drive (SSD) solutions. The stored correlations may be transientdue to change in UDP IP addresses and/or UDP ports associated with theuser devices based at least in part on NAT operation. The time-basedin-memory caching provides a higher data storage layer for optimallystoring the transient data and speedily retrieving the stored data. Inthis way, the meshnet database 112 increases data storage and retrievalperformance by mitigating the need to access underlying slower storagelayers provided by disk solutions and/or by SSD solutions.

In this way, by utilizing the systems and techniques discussed herein,the MSP control infrastructure 104 and the respective clientapplications may enable the user devices included in the mesh network tocontinue to communicate with each other without interruption andmitigate instances of inefficient transmissions and retransmissions ofcommunications among the user devices when respective UDP IP addressesand/or UDP ports change in the mesh network. As a result, the MSPcontrol infrastructure and the respective client applications may enableefficient utilization of user device resources (e.g., processingresources, memory resources, power consumption resources, battery life,or the like) and network resources (computational resources, networkbandwidth, management resources, processing resources, memory resources,or the like) for performing suitable tasks associated with the securemesh network.

As indicated above, FIG. 3 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 3 .

FIG. 4 is an illustration of an example process 400 associated withupdating parameters in a mesh network, according to various aspects ofthe present disclosure. In some aspects, the process 400 may beperformed by a memory and/or a processor/controller (e.g., processingunit 110, processor 820) associated with an MSP control infrastructure(e.g., MSP control infrastructure 104). As shown by reference numeral410, process 400 may include determining, by a processor, firstcommunication information indicating a first communication parameterassociated with a first device and second communication informationindicating a second communication parameter associated with a seconddevice. For instance, the MSP control infrastructure may utilize theassociated memory and/or processor to determine first communicationinformation indicating a first communication parameter associated with afirst device and second communication information indicating a secondcommunication parameter associated with a second device, as discussedelsewhere herein.

As shown by reference numeral 420, process 400 may include transmitting,by the processor, the first communication information to the seconddevice and the second communication information to the first device toenable the first device and the second device to be included in a meshnetwork. For instance, the MSP control infrastructure may utilize anassociated communication interface (e.g., communication interface 870)and the associated memory and/or processor to transmit the firstcommunication information to the second device and the secondcommunication information to the first device to enable the first deviceand the second device to be included in a mesh network, as discussedelsewhere herein.

As shown by reference numeral 430, process 400 may include determining,by the processor during communication between the first device and thesecond device in the mesh network, updated first communicationinformation indicating an updated first communication parameterassociated with the first device and updated second communicationinformation indicating an updated second communication parameterassociated with the second device. For instance, the MSP controlinfrastructure may utilize the associated memory and/or processor todetermine, during communication between the first device and the seconddevice in the mesh network, updated first communication informationindicating an updated first communication parameter associated with thefirst device and updated second communication information indicating anupdated second communication parameter associated with the seconddevice, as discussed elsewhere herein.

As shown by reference numeral 440, process 400 may include transmitting,by the processor, the updated first communication information to thesecond device and the updated second communication information to thefirst device. For instance, the MSP control infrastructure may utilizethe associated communication interface along with the memory and/orprocessor to transmit the updated first communication information to thesecond device and the updated second communication information to thefirst device, as discussed elsewhere herein.

Process 400 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, in process 400, the first communication parameter isa first internet protocol (IP) address or a first IP port utilized bythe first device to communicate in the mesh network and the secondcommunication port is a second IP address or a second IP port utilizedby the second device to communicate in the mesh network.

In a second aspect, alone or in combination with the first aspect, inprocess 400, the first communication parameter is a first user datagramprotocol (UDP) internet protocol (IP) address or a first UDP portutilized by the first device to communicate in the mesh network and thesecond communication port is a second UDP IP address or a second UDPport utilized by the second device to communicate in the mesh network.

In a third aspect, alone or in combination with the first through secondaspects, process 400 may include determining a first meshnet internetprotocol (IP) address to be utilized by the first device to communicatein the mesh network and a second meshnet IP address to be utilized bythe second device to communicate in the mesh network; and transmittingthe first meshnet IP address to the second device and the second meshnetIP address to the first device.

In a fourth aspect, alone or in combination with the first through thirdaspects, process 400 may include receiving, during communication betweenthe first device and the second device in the mesh network, a firstrequest from the first device and a second request from the seconddevice, wherein determining the updated first communication informationincludes determining the updated first communication information basedat least in part on the first request and determining the updated secondcommunication information includes determining the updated secondcommunication information based at least in part on the second request.

In a fifth aspect, alone or in combination with the first through fourthaspects, process 400 may include storing, by the processor in a memory,a first correlation between the first communication information and thefirst device; and updating, by the processor in the memory, the firstcorrelation by replacing the first communication information with thefirst updated communication information.

In a sixth aspect, alone or in combination with the first through fifthaspects, in process 400, the communication between the first device andthe second device in the mesh network includes a communication usinguser datagram protocol (UDP).

Although FIG. 4 shows example blocks of the process, in some aspects,the process may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 4 .Additionally, or alternatively, two or more of the blocks of the processmay be performed in parallel.

As indicated above, FIG. 4 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 4 .

FIG. 5 is an illustration of an example process 500 associated withupdating parameters in a mesh network, according to various aspects ofthe present disclosure. In some aspects, the process 500 may beperformed by a memory and/or a processor/controller (e.g., processingunit 110, processor 820) associated with an MSP control infrastructure(e.g., MSP control infrastructure 104). As shown by reference numeral510, process 500 may include determining, by a processor, a firstcommunication parameter associated with a first device and a secondcommunication parameter associated with a second device, the firstdevice and second device communicating data over a meshnet connectionassociated with a mesh network. For instance, the MSP controlinfrastructure may utilize the associated memory and/or processor todetermine a first communication parameter associated with a first deviceand a second communication parameter associated with a second device,the first device and second device communicating data over a meshnetconnection associated with a mesh network, as discussed elsewhereherein.

As shown by reference numeral 520, process 500 may include storing, bythe processor in a memory, a first correlation including the firstcommunication parameter and the first device and a second correlationincluding the second communication parameter and the second device. Forinstance, the MSP control infrastructure may utilize the associatedmemory and/or processor to store, in a memory, a first correlationincluding the first communication parameter and the first device and asecond correlation including the second communication parameter and thesecond device, as discussed elsewhere herein.

As shown by reference numeral 530, process 500 may include updating, bythe processor in the memory, the first communication parameter in thefirst correlation based at least in part on determining a change in thefirst communication parameter or the second communication parameter inthe second correlation based at least in part on determining a change inthe second communication parameter. For instance, the MSP controlinfrastructure may utilize the associated memory and/or processor toupdate, in the memory, the first communication parameter in the firstcorrelation based at least in part on determining a change in the firstcommunication parameter or the second communication parameter in thesecond correlation based at least in part on determining a change in thesecond communication parameter, as discussed elsewhere herein.

Process 500 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, in process 500, the first communication parameterincludes a first internet protocol (IP) address or a first IP portutilized by the first device to communicate in the mesh network and thesecond communication parameter includes a second IP address or a secondIP port utilized by the second device to communicate in the meshnetwork.

In a second aspect, alone or in combination with the first aspect, inprocess 500, updating the first correlation or the second correlationincludes updating the first correlation or the second correlation duringcommunication of the data by the first device and the second device inthe mesh network.

In a third aspect, alone or in combination with the first through secondaspects, process 500 may include receiving, during communication of thedata in the mesh network, a first request to determine the firstcommunication parameter or a second request to determine the secondcommunication parameter.

In a fourth aspect, alone or in combination with the first through thirdaspects, process 500 may include determining a first meshnet internetprotocol (IP) address to be utilized by the first device to communicatein the mesh network and a second meshnet IP address to be utilized bythe second device to communicate in the mesh network; and transmittingthe first meshnet IP address to the second device and the second meshnetIP address to the first device.

In a fifth aspect, alone or in combination with the first through fourthaspects, in process 500, the first device and the second devicecommunicate the data in the mesh network using a user datagram protocol(UDP).

In a sixth aspect, alone or in combination with the first through fifthaspects, in process 500, the memory is configured to enable speedyretrieval of information.

Although FIG. 5 shows example blocks of the process, in some aspects,the process may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 5 .Additionally, or alternatively, two or more of the blocks of the processmay be performed in parallel.

As indicated above, FIG. 5 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 5 .

FIG. 6 is an illustration of an example process 600 associated withupdating parameters in a mesh network, according to various aspects ofthe present disclosure. In some aspects, the process 600 may beperformed by a memory and/or a processor/controller (e.g., processingunit 116, processor 820) associated with a user device (e.g., userdevice 102) executing a client application. As shown by referencenumeral 610, process 600 may include communicating, by a first device,data with a second device based at least in part on communicationinformation indicating a communication parameter associated with thesecond device, the data being communicated over a meshnet connectionassociated with a mesh network. For instance, the user device mayutilize an associated communication interface (e.g., communicationinterface 870) along with the memory and/or processor to communicate(e.g., transmit and/or receive) data with a second device based at leastin part on communication information indicating a communicationparameter associated with the second device, the data being communicatedover a meshnet connection associated with a mesh network, as discussedelsewhere herein.

As shown by reference numeral 620, process 600 may include receiving, bythe first device while communicating the data in the mesh network,updated communication information indicating an updated communicationparameter associated with the second device. For instance, the userdevice may utilize the associated communication interface, memory,and/or processor to receive, while communicating the data in the meshnetwork, updated communication information indicating an updatedcommunication parameter associated with the second device, as discussedelsewhere herein.

As shown by reference numeral 630, process 600 may includecommunicating, by the first device, the data with the second device overthe meshnet connection based at least in part on the updatedcommunication information. For instance, the user device may utilize theassociated communication interface, memory, and/or processor tocommunicate (e.g., transmit and/or receive) the data with the seconddevice over the meshnet connection based at least in part on the updatedcommunication information, as discussed elsewhere herein.

Process 600 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, in process 600, the communication parameter includesa second internet protocol (IP) address or a second IP port utilized bythe second device to communicate in the mesh network.

In a second aspect, alone or in combination with the first aspect, inprocess 600, the communication parameter includes a second user datagramprotocol (UDP) internet protocol (IP) address or a second UDP portutilized by the second device to communicate in the mesh network.

In a third aspect, alone or in combination with the first through secondaspects, process 600 may include transmitting, to an infrastructuredevice, a request for the infrastructure device to determine a firstinternet protocol (IP) address or a first IP port utilized by the firstdevice to communicate in the mesh network.

In a fourth aspect, alone or in combination with the first through thirdaspects, process 600 may include encrypting, based at least in part onutilizing a public key associated with the second device, a messageassociated with setting up the meshnet connection; and transmitting theencrypted message to the second device.

In a fifth aspect, alone or in combination with the first through fourthaspects, process 600 may include negotiating, with the second device, asymmetric key to be utilized to communicate encrypted data over themeshnet connection.

In a sixth aspect, alone or in combination with the first through fifthaspects, process 600 may include determining a key pair to be utilizedduring setting up the meshnet connection, the key pair including apublic key and a private key.

Although FIG. 6 shows example blocks of the process, in some aspects,the process may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 6 .Additionally, or alternatively, two or more of the blocks of the processmay be performed in parallel.

As indicated above, FIG. 6 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 6 .

FIG. 7 is an illustration of an example process 700 associated withupdating parameters in a mesh network, according to various aspects ofthe present disclosure. In some aspects, the process 700 may beperformed by a memory and/or a processor/controller (e.g., processingunit 116, processor 820) associated with a user device (e.g., userdevice 102) executing a client application. As shown by referencenumeral 710, process 700 may include communicating, by a first devicewith a second device, data over a meshnet connection in a mesh network.For instance, the user device may utilize an associated communicationinterface (e.g., communication interface 870) and the associated memoryand/or processor to communicate (e.g., transmit and/or receive), with asecond device, data over a meshnet connection in a mesh network, asdiscussed elsewhere herein.

As shown by reference numeral 720, process 700 may include selectivelytransmitting, by the first device in the mesh network, a request todetermine a communication parameter associated with the first device,the selectively transmitting including refraining from transmitting therequest based at least in part on determining that a conditionassociated with transmitting the request is satisfied. For instance, theuser device may utilize the associated memory and/or processor toselectively transmit, in the mesh network, a request to determine acommunication parameter associated with the first device, theselectively transmitting including refraining from transmitting therequest based at least in part on determining that a conditionassociated with transmitting the request is satisfied, as discussedelsewhere herein.

Process 700 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, in process 700, determining that the condition issatisfied includes determining that the first device is activelycommunicating data with the second device.

In a second aspect, alone or in combination with the first aspect, inprocess 700, determining that the condition is satisfied includesdetermining that the first device does not anticipate communicating datawith the second device for a given interval of time.

In a third aspect, alone or in combination with the first through secondaspects, in process 700, selectively transmitting the request includestransmitting the request periodically.

In a fourth aspect, alone or in combination with the first through thirdaspects, in process 700, the communication parameter includes a firstinternet protocol (IP) address or a first IP port utilized by the firstdevice to communicate data in the mesh network.

In a fifth aspect, alone or in combination with the first through fourthaspects, in process 700, communicating the data includes encrypting thedata based at least in part utilizing a symmetric key.

In a sixth aspect, alone or in combination with the first through fifthaspects, process 700 may include receiving, by the first device in themesh network, updated communication information indicating an updatedcommunication parameter associated with the second device; andcommunicating, by the first device with the second device, the data inthe mesh network based at least in part on utilizing the updatedcommunication parameter.

Although FIG. 7 shows example blocks of the process, in some aspects,the process may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 7 .Additionally, or alternatively, two or more of the blocks of the processmay be performed in parallel.

As indicated above, FIG. 7 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 7 .

FIG. 8 is an illustration of example devices 800 associated withupdating parameters in a mesh network, according to various aspects ofthe present disclosure. In some aspects, the example devices 800 mayform part of or implement the systems, servers, environments,infrastructures, components, devices, or the like described elsewhereherein (e.g., MSP control infrastructure, user device, etc.) and may beused to perform example processes described elsewhere herein. Theexample devices 800 may include a universal bus 810 communicativelycoupling a processor 820, a memory 830, a storage component 840, aninput component 850, an output component 860, and a communicationinterface 870.

Bus 810 may include a component that permits communication amongmultiple components of a device 800. Processor 820 may be implemented inhardware, firmware, and/or a combination of hardware and software.Processor 820 may take the form of a central processing unit (CPU), agraphics processing unit (GPU), an accelerated processing unit (APU), amicroprocessor, a microcontroller, a digital signal processor (DSP), afield-programmable gate array (FPGA), an application-specific integratedcircuit (ASIC), or another type of processing component. In someaspects, processor 820 may include one or more processors capable ofbeing programmed to perform a function. Memory 830 may include a randomaccess memory (RAM), a read only memory (ROM), and/or another type ofdynamic or static storage device (e.g., a flash memory, a magneticmemory, and/or an optical memory) that stores information and/orinstructions for use by processor 820.

Storage component 840 may store information and/or software related tothe operation and use of a device 800. For example, storage component840 may include a hard disk (e.g., a magnetic disk, an optical disk,and/or a magneto-optic disk), a solid state drive (SSD), a compact disc(CD), a digital versatile disc (DVD), a floppy disk, a cartridge, amagnetic tape, and/or another type of non-transitory computer-readablemedium, along with a corresponding drive.

Input component 850 may include a component that permits a device 800 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 850 mayinclude a component for determining location (e.g., a global positioningsystem (GPS) component) and/or a sensor (e.g., an accelerometer, agyroscope, an actuator, another type of positional or environmentalsensor, and/or the like). Output component 860 may include a componentthat provides output information from device 800 (via, for example, adisplay, a speaker, a haptic feedback component, an audio or visualindicator, and/or the like).

Communication interface 870 may include a transceiver-like component(e.g., a transceiver, a separate receiver, a separate transmitter,and/or the like) that enables a device 800 to communicate with otherdevices, such as via a wired connection, a wireless connection, or acombination of wired and wireless connections. Communication interface870 may permit device 800 to receive information from another deviceand/or provide information to another device. For example, communicationinterface 870 may include an Ethernet interface, an optical interface, acoaxial interface, an infrared interface, a radio frequency (RF)interface, a universal serial bus (USB) interface, a Wi-Fi interface, acellular network interface, and/or the like.

A device 800 may perform one or more processes described elsewhereherein. A device 800 may perform these processes based on processor 820executing software instructions stored by a non-transitorycomputer-readable medium, such as memory 830 and/or storage component840. As used herein, the term “computer-readable medium” may refer to anon-transitory memory device. A memory device may include memory spacewithin a single physical storage device or memory space spread acrossmultiple physical storage devices.

Software instructions may be read into memory 830 and/or storagecomponent 840 from another computer-readable medium or from anotherdevice via communication interface 870. When executed, softwareinstructions stored in memory 830 and/or storage component 840 may causeprocessor 820 to perform one or more processes described elsewhereherein. Additionally, or alternatively, hardware circuitry may be usedin place of or in combination with software instructions to perform oneor more processes described elsewhere herein. Thus, implementationsdescribed herein are not limited to any specific combination of hardwarecircuitry and software.

The quantity and arrangement of components shown in FIG. 8 are providedas an example. In practice, a device 800 may include additionalcomponents, fewer components, different components, or differentlyarranged components than those shown in FIG. 8 . Additionally, oralternatively, a set of components (e.g., one or more components) of adevice 800 may perform one or more functions described as beingperformed by another set of components of a device 800.

As indicated above, FIG. 8 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 8 .

Persons of ordinary skill in the art will appreciate that the aspectsencompassed by the present disclosure are not limited to the particularexemplary aspects described herein. In that regard, althoughillustrative aspects have been shown and described, a wide range ofmodification, change, and substitution is contemplated in the foregoingdisclosure. It is understood that such variations may be made to theaspects without departing from the scope of the present disclosure.Accordingly, it is appropriate that the appended claims be construedbroadly and in a manner consistent with the present disclosure.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the aspects to the preciseform disclosed. Modifications and variations may be made in light of theabove disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” or “device” is intended to bebroadly construed as hardware, firmware, or a combination of hardwareand software. As used herein, a processor is implemented in hardware,firmware, or a combination of hardware and software.

As used herein, satisfying a threshold may, depending on the context,refer to a value being greater than the threshold, greater than or equalto the threshold, less than the threshold, less than or equal to thethreshold, equal to the threshold, or not equal to the threshold, amongother examples, or combinations thereof.

It will be apparent that systems or methods described herein may beimplemented in different forms of hardware, firmware, or a combinationof hardware and software. The actual specialized control hardware orsoftware code used to implement these systems or methods is not limitingof the aspects. Thus, the operation and behavior of the systems ormethods were described herein without reference to specific softwarecode—it being understood that software and hardware can be designed toimplement the systems or methods based, at least in part, on thedescription herein.

Even though particular combinations of features are recited in theclaims or disclosed in the specification, these combinations are notintended to limit the disclosure of various aspects. In fact, many ofthese features may be combined in ways not specifically recited in theclaims or disclosed in the specification. Although each dependent claimlisted below may directly depend on only one claim, the disclosure ofvarious aspects includes each dependent claim in combination with everyother claim in the claim set. A phrase referring to “at least one of” alist of items refers to any combination of those items, including singlemembers. As an example, “at least one of: a, b, or c” is intended tocover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination withmultiples of the same element (for example, a-a, a-a-a, a-a-b, a-a-c,a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering ofa, b, and c).

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterm “set” is intended to include one or more items (e.g., relateditems, unrelated items, a combination of related and unrelated items,etc.), and may be used interchangeably with “one or more.” Where onlyone item is intended, the phrase “only one” or similar language is used.Also, as used herein, the terms “has,” “have,” “having,” or the like areintended to be open-ended terms. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise. Also, as used herein, the term “or” is intended to beinclusive when used in a series and may be used interchangeably with“and/or,” unless explicitly stated otherwise (e.g., if used incombination with “either” or “only one of”).

What is claimed is:
 1. A method, comprising: receiving, by a first device based at least in part on a first request transmitted in a mesh network, communication information indicating a communication parameter associated with a second device in the mesh network; communicating, by the first device with the second device in the mesh network, encrypted data based at least in part on utilizing the communication parameter associated with the second device, the encrypted data being determined based at least in part on utilizing a symmetric key to encrypt data and being communicated over a meshnet connection associated with the mesh network; receiving, by the first device while communicating the encrypted data in the mesh network and based at least in part on a second request transmitted in the mesh network, updated communication information indicating an updated communication parameter associated with the second device; and communicating, by the first device with the second device in the mesh network, the encrypted data over the meshnet connection based at least in part on utilizing the updated communication parameter.
 2. The method of claim 1, wherein the communication parameter includes an internet protocol (IP) address or an IP port utilized by the second device to communicate in the mesh network.
 3. The method of claim 1, wherein the communication parameter includes a user datagram protocol (UDP) internet protocol (IP) address or a UDP IP port utilized by the second device to communicate in the mesh network.
 4. The method of claim 1, further comprising: transmitting, to an infrastructure device, a request for the infrastructure device to determine an internet protocol (IP) address or an IP port utilized by the first device to communicate in the mesh network.
 5. The method of claim 1, further comprising: encrypting, based at least in part on utilizing a public key associated with the second device, a message associated with setting up the meshnet connection; and transmitting the encrypted message to the second device.
 6. The method of claim 1, further comprising: negotiating, with the second device, the symmetric key to be utilized to communicate the encrypted data over the meshnet connection.
 7. The method of claim 1, further comprising: determining a key pair to be utilized during setting up the meshnet connection, the key pair including a public key and a private key.
 8. A first device, comprising: a memory; and a processor communicatively coupled to the memory, the memory and the processor being configured to: receive, based at least in part on a first request transmitted in a mesh network, communication parameter associated with a second device in the mesh network; communicate encrypted data with the second device based at least in part on utilizing the communication parameter associated with the second device, the encrypted data being determined based at least in part on utilizing a symmetric key to encrypt data and being communicated over a meshnet connection associated with the mesh network; receive, while communicating the encrypted data in the mesh network and based at least in part on a second request transmitted in the mesh network, updated communication information indicating an updated communication parameter associated with the second device; and communicate, with the second device in the mesh network, the encrypted data over the meshnet connection based at least in part on utilizing the updated communication parameter.
 9. The first device of claim 8, wherein the communication parameter includes an internet protocol (IP) address or an IP port utilized by the second device to communicate in the mesh network.
 10. The first device of claim 8, wherein the communication parameter includes a user datagram protocol (UDP) internet protocol (IP) address or a UDP IP port utilized by the second device to communicate in the mesh network.
 11. The first device of claim 8, wherein the memory and the processor are configured to: transmit, to an infrastructure device, a request for the infrastructure device to determine an internet protocol (IP) address or an IP port utilized by the first device to communicate in the mesh network.
 12. The first device of claim 8, wherein the memory and the processor are configured to: encrypt, based at least in part on utilizing a public key associated with the second device, a message associated with setting up the meshnet connection; and transmit the encrypted message to the second device.
 13. The first device of claim 8, wherein the memory and the processor are configured to: negotiate, with the second device, the symmetric key to be utilized to communicate the encrypted data over the meshnet connection.
 14. The first device of claim 8, wherein the memory and the processor are configured to: determine a key pair to be utilized during setting up the meshnet connection, the key pair including a public key and a private key.
 15. A non-transitory computer-readable medium configured to store instructions, which when executed by a processor associated with a first device, configure the processor to: receive, based at least in part on a first request transmitted in a mesh network, communication parameter associated with a second device in the mesh network; communicate encrypted data with the second device based at least in part on utilizing the communication parameter associated with the second device, the encrypted data being determined based at least in part on utilizing a symmetric key to encrypt data and being communicated over a meshnet connection associated with the mesh network; receive, while communicating the encrypted data in the mesh network and based at least in part on a second request transmitted in the mesh network, updated communication information indicating an updated communication parameter associated with the second device; and communicate, with the second device in the mesh network, the encrypted data over the meshnet connection based at least in part on utilizing the updated communication parameter.
 16. The non-transitory computer-readable medium of claim 15, wherein the communication parameter includes an internet protocol (IP) address or an IP port utilized by the second device to communicate in the mesh network.
 17. The non-transitory computer-readable medium of claim 15, wherein the communication parameter includes a user datagram protocol (UDP) internet protocol (IP) address or a UDP IP port utilized by the second device to communicate in the mesh network.
 18. The non-transitory computer-readable medium of claim 15, wherein the processor is configured to: transmit, to an infrastructure device, a request for the infrastructure device to determine an internet protocol (IP) address or an IP port utilized by the first device to communicate in the mesh network.
 19. The non-transitory computer-readable medium of claim 15, wherein the processor is configured to: encrypt, based at least in part on utilizing a public key associated with the second device, a message associated with setting up the meshnet connection; and transmit the encrypted message to the external device.
 20. The non-transitory computer-readable medium of claim 15, wherein the processor is configured to: negotiate, with the second device, the symmetric key to be utilized to communicate the encrypted data over the meshnet connection, or determine a key pair to be utilized during setting up the meshnet connection, the key pair including a public key and a private key. 